home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.20021006-20030409
/
000342_fdc@columbia.edu_Fri Feb 28 10:21:02 EST 2003.msg
< prev
next >
Wrap
Text File
|
2003-04-08
|
3KB
|
64 lines
Article: 14139 of comp.protocols.kermit.misc
Path: newsmaster.cc.columbia.edu!news.columbia.edu!news-not-for-mail
From: fdc@columbia.edu (Frank da Cruz)
Newsgroups: comp.unix.sco.misc,comp.protocols.kermit.misc
Subject: SCOANSI vs ANSI vs mapchan
Date: 28 Feb 2003 09:47:30 -0500
Organization: Columbia University
Lines: 48
Message-ID: <b3nsq2$5nd$1@watsol.cc.columbia.edu>
NNTP-Posting-Host: watsol.cc.columbia.edu
X-Trace: newsmaster.cc.columbia.edu 1046443652 19633 128.59.39.139 (28 Feb 2003 14:47:32 GMT)
X-Complaints-To: postmaster@columbia.edu
NNTP-Posting-Date: 28 Feb 2003 14:47:32 GMT
Xref: newsmaster.cc.columbia.edu comp.unix.sco.misc:154009 comp.protocols.kermit.misc:14139
Tech-support issue of the week... Kermit 95:
http://www.columbia.edu/kermit/k95.html
includes an SCO ANSI terminal emulator. When making a Telnet, Rlogin, or
SSH connection to an SCO platform, K95 sends the terminal type name.
To get the desired emalution (SCO function keys, special escape sequences,
etc), the user must choose the K95 terminal type called SCOANSI, as opposed
to "regular" ANSI, which is the original "BBS ANSI" that is only a small
subset of SCOANSI. However, most SCO operating systems do not understand
"SCOANSI" (this issue has been discussed here before, and I believe the
problem was fixed in newer SCO operating systems).
When the SCO OS does not understand "SCOANSI", our advice is to tell K95
to tell the server its type is "ANSI". The K95 commands are:
set terminal type scoansi ; What I am
set telnet terminal-type ansi ; What I say I am
(the latter command applies to SSH and Rlogin too).
As far as I know, this has worked for years. But suddenly we're getting
reports of fractured screens and failing file transfers from people who
do this, e.g. on Open Server 5.0.5. Either something has changed on the
SCO end or people have been having problems all along but not reporting
them. If I tell the user to tell the SCO OS to:
mapchan -n
the problems go away. Similarly, if the user omits the "set telnet
terminal-type ansi" command, the problems go away (but then they have
to set their terminal type manually at the SCO shell prompt).
My questions are these:
1. Exactly which SCO operating systems understand the name "SCOANSI"?
2. Does the SCO Telnet (Rlogin, SSH) server, when it is told by the
client that terminal type is ANSI, activate mapchan?
3. If the answer to (2) is yes, is "ANSI" the only terminal-type name
that causes this to happen?
Thanks.
- Frank